Q When you spot a kerning problem in a document and want to fix it, why should you have to go outside the page to another program, where you identify a font file, open it, and type in or select the problem pair?
A All you should have to do is point to it in the document. Your computer knows what font and pair you’re talking about!
 
Q You may want to store kern pairs in a font suitcase file. Kerning tables in a font suitcase file are available to any application which wants to use them. The container is flexible, allowing custom kern sets to be stored and managed easily by just renaming the file. The files are small and easily transportable. Why should you have to close the font file on your system, open it in a separate application, and edit the pairs there?
A The file is open now!
 
Q You may want to save extended kerning tables with a document, and with XPress 3.1 you can. Doing so 1 makes sense if you're sending the file out for editing or reproduction since it eliminates the need for a font suitcase file (and the less pieces to remember, the less to forget); 2 guarantees the integrity of the document weeks, or years from now, though your kerning tables will have since evolved; 3 offers a location for custom kerning not applicable elsewhere. Why should you have to fight to get the table into XPress Preferences, so you can then Save it with the document?
A See the illustration above. You're already using that table!
